Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Do not include Facebook license on users codegen'd code #32840

Closed
wants to merge 1 commit into from

Conversation

cortinico
Copy link
Contributor

Summary:
Closes #31516
I've cherry-picked the original PR that had merge conficts + updated all
the headers as the one for the TurboModule generators were not handled.

Original Commit Message from acoates

The codegen generates a Facebook copyright notice at the top of the generated files.

While this might make sense on the core files, this codegen will be run on external components too.
The notice also refers to a LICENSE file in the root of this project, which might not be there if this is run on another project.
I did a quick look at some of the codegen that we ship within windows dev tools, and it looks like we normally just have comments
saying the file was codegen'd and so the file shouldn't be manually edited.
Open to suggestions on what the comment header should say.

Changelog:
[General] [Changed] - Do not include Facebook license on users codegen'd code

Differential Revision: D33455176

@facebook-github-bot facebook-github-bot added CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. p: Facebook Partner: Facebook Partner fb-exported labels Jan 6, 2022
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D33455176

@analysis-bot
Copy link

analysis-bot commented Jan 6, 2022

Platform Engine Arch Size (bytes) Diff
ios - universal n/a --

Base commit: ca5aaa7
Branch: main

@analysis-bot
Copy link

analysis-bot commented Jan 6, 2022

Platform Engine Arch Size (bytes) Diff
android hermes arm64-v8a 8,289,885 +0
android hermes armeabi-v7a 7,624,822 +0
android hermes x86 8,762,300 +0
android hermes x86_64 8,699,301 +0
android jsc arm64-v8a 9,678,193 +0
android jsc armeabi-v7a 8,669,807 +0
android jsc x86 9,636,108 +0
android jsc x86_64 10,230,705 +0

Base commit: ca5aaa7
Branch: main

Summary:
Pull Request resolved: facebook#32840

Closes facebook#31516
I've cherry-picked the original PR that had merge conficts + updated all
the headers as the one for the TurboModule generators were not handled.

Original Commit Message from acoates

The codegen generates a Facebook copyright notice at the top of the generated files.

While this might make sense on the core files, this codegen will be run on external components too.
The notice also refers to a LICENSE file in the root of this project, which might not be there if this is run on another project.
I did a quick look at some of the codegen that we ship within windows dev tools, and it looks like we normally just have comments
saying the file was codegen'd and so the file shouldn't be manually edited.
Open to suggestions on what the comment header should say.

Changelog:
[General] [Changed] - Do not include Facebook license on users codegen'd code

Differential Revision: D33455176

fbshipit-source-id: 5bcc73155d79ee7128726ec040bb6a5f94623baf
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D33455176

@react-native-bot
Copy link
Collaborator

This pull request was successfully merged by @cortinico in 4509679.

When will my fix make it into a release? | Upcoming Releases

@react-native-bot react-native-bot added the Merged This PR has been merged. label Jan 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. fb-exported Merged This PR has been merged. p: Facebook Partner: Facebook Partner
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants